CPS-0001 | Metadata Discoverability and Trust #371
Conversation
ehanoc
changed the title
rphair
changed the title
rphair
changed the title
|
among other things, this relates to our currently open CIP's that address identity for individuals (creators / authors) & stake pools: |
| - Trust can be anchored to the owner's metadata or also third-parties that attest for the correctness of the metadata. How to handle this? | ||
| - How to associate identity to a metadata claim? | ||
| - How to handle the case where a subject has multiple metadata claims associated with it? | ||
| - How to handle the case where a subject has multiple metadata claims associated with it and the user wants to select a specific one? |
There was a problem hiding this comment.
Please re-order the sections as per the latest structure 🙏 (and apologies for this, I guess that goes with being one of the first CPS pioneers!):
- Abstract
- Problem
- Use Cases
- Goals
- Open Questions
Also, given the numerous proposed solutions; it might help to formulate what part of the problem remains to be solved and what parts have been properly addressed already.
There was a problem hiding this comment.
Also, given the numerous proposed solutions; it might help to formulate what part of the problem remains to be solved and what parts have been properly addressed already.
Great @KtorZ ; i think here there some attempts in coming out with some solutions (i.e token metadata, off chain storage[cip-26]), for very specific use cases but not to the general problem of discovering, verifying and asserting trust in metadata?
Maybe someone can help me by pointing out current solutions / implementations, that in their opinion, are working well for a specific context. And those can provide lessons to try tackle this in a more generalized way.
There was a problem hiding this comment.
What I meant was that, the current document lists several CIPs as "proposed solutions"; which implies that the listed proposals address either partially or fully the problem. If they are simply related to the problem, but not actual solutions to it, then I'd suggest to move them elsewhere (i.e. in the problem statement itself, if those existing efforts and their shortcomings are worth mentioning).
(note: I haven't reviewed the statement yet, nor any of the linked PR; so I am mostly speculating here. My gut feeling being that this particular CPS is about some dimensions of metadata -- discoverability and trust -- that existing CIPs do not address properly. Hence, they shouldn't be listed as 'proposed solutions' because none of them is about solving the discoverability and trust problem in the metadata landscape -- except maybe CIP-0068 in some sense?)
KtorZ
changed the title
| ## **Problem** | ||
| **`Discoverability`**: Means to discover the different metadata claims associated with a subject. Discoverability is important for wallets, applications (i.e dapps, stores, etc) and users to be able to find the different metadata claims associated with a subject. This is important for the user to be able to make an informed decision on how to interact with a subject. | ||
|
|
||
| **`Correctness`**: Lack of mechanism to assert that a given metadata claim is correct. Anybody and any service can provide metadata structures, but it's necessary to attest for the correctness of this metadata so that the user (or applications) are be able to make an informed decision in accepting, rejecting or how to interact with a subject. |
There was a problem hiding this comment.
Would the "metadata is up to date" be part of correctness or discoverability? or neither?
There was a problem hiding this comment.
"Up to date" to a given point in time? In my mind whatever is anchored on chain is "up to date" and if there will be updates; we need mechanisms to discovery / be notified of new versions. Makes sense?
Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>
Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>
Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>
Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>
Co-authored-by: Ryan Williams <44342099+Ryun1@users.noreply.github.com>
| - Associate some form of identity to a metadata claim | ||
|
|
||
| ## **Open Questions** | ||
| - Is this a combination of problems and should be split into multiple CPS? |
There was a problem hiding this comment.
Is this a combination of problems and should be split into multiple CPS?
It might make sense to split this problem by metadata subject i.e. stake pools, tokens, scripts, etc. As the problem can be solved quite differently for each of these entities.
Without the historical context for CPSs its hard to know how wide the scope should be.
CPS-01 Added discussion of existing solutions
|
I believe the beacon token CIP here addresses pretty much all of your use cases. I have created reference implementations that do similar things.
Beacon tokens are extremely generalizable. Do you agree that they address your use cases? Or am I misunderstanding something? |
|
To further highlight the generalizability of beacon tokens, I used beacon tokens to create cardano-swaps. It is a distributed DEX proof-of-concept where users maintain full delegation control and custody of their assets at all times. Thanks to beacon tokens, no batchers are needed. Instead, users lookup the beacon tokens to find each other (and the relevant information to execute swaps) in a p2p manner. |
|
FYI @ehanoc the fact that a candidate CIP is relevant to this CPS came up in today's CIP Editors' Meeting (cc @KtorZ @Ryun1): #467 (comment) |
KtorZ
added
the
Category: Metadata
|
@Ryun1 @Crypto2099 it seems a shame that CPS-0001 never went anywhere but @ehanoc I have to assume this has been abandoned at least due to personnel changes. @fallen-icarus in the unlikely event that you want something extra on your plate, you would have my full confidence to advocate & continue this submission: or perhaps just to tag anyone else who might be interested in reopening & completing it. |
rphair
added
the
State: Likely Abandoned
|
I would like to pick this one back up, when I have time :) |
There seems to be multiple proposals and attempts to solve issues around metadata specific to certain contexts. Proposing this as a first CPS in order for us to agree what the general problem actually is and try to steer the process to tackle the root cause of the problem. This is my attempt at describing the problem.
(current draft in branch)